I already have "never warn me about suspicious activity" selected.  I have a database running in MS Access 2010 which is generating a bunch of reports, some of which are being emailed off, and I keep getting this message ever since I moved to Office 365 and outlook 2013.  Running on Windows 7

Thanx

Phil

Hello,

You should try these steps:

Open MS Outlook >> Click on File Tab >> Options >>Click on Trust Center >> Trust Center Settings (at right pane)>> Programmatic Access >> Select the option as Shown in Screen Shot >> Click OK.

To know more, click here: http://www.msoutlook.info/question/883

Thanks & Regards

Clark Kent

 I have a database running in MS Access 2010 which is generating a bunch of reports, some of which are being emailed off, and I keep getting this message ever since I moved to Office 365 and outlook 2013. 

If you run this using Access 2013 instead of 2010 - do you get the same result?

I have made those changes and we will see what happens tomorrow.

I don't understand why this would work but "Never warn me..." would not.  then again, there is a lot of stuff that does not make sense to me about Microsoft products.

I don't know.  I am not ready to move this into 2013 as of yet.  I have no time to go fix anythign that 2013 would break.

Ok, I was able to rerun my report routine after making that change, and it did not make a difference,  i am still being asked to allow the program access to send an email

I don't know.  I am not ready to move this into 2013 as of yet.  I have no time to go fix anythign that 2013 would break.

Purpose of the question was to eliminate the possibility that the issue stems from a <side-by-side> install of Office '2010 and Office '2013 - no more - no less. A little confused as to why it would be difficult to simply run the same thing using Access '2013. If it doesn't work - it doesn't work but seems logical that would be something that you'd at the very least would want to know about unless you are permanently planning on have 2 versions of MS Access installed.

If running these reports works when run from Access '2013 - source of the problem is identified which also means it's not an Outlook '2013 related issue. If the only problem you encounter is the security prompt - then the Access related forum might be a better place to ask about it so see if anyone else has encountered the problem in a "side-by-side" configuration and how (if) they got around it.

Yes, 2010 and 2013 are installed on the same machine.  I can launch it from 2013 to see if it would make a difference.  Just not ready to permanently move it over to 2013. I just gave that a try and am still running into the same issue even with 2013.

I am curious how it could be something other than an Outlook problem, since Outlook is generating the dialog Box, and I had (I thought,) specifically disabled that dialog box from within Outlook.

However, If you think it is worthwhile, I would be happy to post over in Access

Yes, 2010 and 2013 are installed on the same machine.  I can launch it from 2013 to see if it would make a difference.  Just not ready to permanently move it over to 2013. I just gave that a try and am still running into the same issue even with 2013.

I am curious how it could be something other than an Outlook problem, since Outlook is generating the dialog Box, and I had (I thought,) specifically disabled that dialog box from within Outlook.

However, If you think it is worthwhile, I would be happy to post over in Access

Don't definitively know whether the "side by side" configuration is a factor or not but you do have 2 versions of Outlook installed which may or may not come down to how Outlook is getting invoked from within Access or more importantly/specifically - how the contact items is being accessed (been a long time since I've actually developed anything using Access).

Two versions of Access.  Only one version of Outlook.

I already have "never warn me about suspicious activity" selected in Outlook, yet Access 2010 and 2013 trigger this "a program is trying to send an e-mail" dialog box.  I need it to stop.

Any ideas?

Phil

• Merged by Steve FanMicrosoft contingent staff, Moderator 5 hours 56 minutes ago duplicate post

I already have "never warn me about suspicious activity" selected in Outlook, yet Access 2010 and 2013 trigger this "a program is trying to send an e-mail" dialog box.  I need it to stop.

Any ideas?

Phil

• Merged by Steve FanMicrosoft contingent staff, Moderator Tuesday, September 01, 2015 1:34 AM duplicate post

One option is to use the Outlook add-in Express ClickYes (not free).

Another is to rewrite the code that sends e-mail using Outlook Redemption.

Two versions of Access.  Only one version of Outlook.

Out of curiosity

1) How are you accessing/traversing the contacts being emailed from within Access
        a) via a linked table to a contact folder or
        b) via OOM using VBA or............

2) Was '2013 installed from an ISO build which removed Outlook or from a C2R installation and you removed Outlook yourself (beforehand? or afterwards?)

However, like I said, don't know if the '2010/2013 scenario is remotely at the root of this but it can't be discounted

What kind of changes are we talking about?  I probably email a dozen reports from this one process.  I get that I would have to download and install this library, and convert all of my macros to VBA code, but after that, how much coding do I have to do be beyond a basic "sendmail" command?

So is what you are telling me is that the option setting in Outlook 2013 "never warn me about suspicious activity" is useless?

On my computer, this setting is grayed out because Outlook has determined that my antivirus software is OK:

As a result I don't get the warnings. Is there something wrong with your antivirus protection?

1) I am not.  All of the Email addresses being used are hardcoded in.

2) Seems to be a little confusion here.  2010 was installed by CD years ago.  Outlook 2010 was never installed as we were a Groupwise house.  Yes, we deliberately excluded it frm the instalation process. 

2013 was installed Click to RUn from Office 365, and Outlook was installed as well because we moved to Exchange online as part of our office 365 migration.

The only version of outlook that has ever been on this machine is the install of 2013.

Your setting is most likely greyed out because you are not running Outlook as an administrator.  Like yours, outlook shows my antivirus status as Valid.  Plus, if I choose "Never warn me.." then I would expect to NEVER get those warnings.  Instead I get them about a dozen times every single morning, which is problematic because all of these reports are supposed to be completed BEFORE I GET IN.

Phil

1) I am not.  All of the Email addresses being used are hardcoded in.

2) Seems to be a little confusion here.  2010 was installed by CD years ago.  Outlook 2010 was never installed as we were a Groupwise house.  Yes, we deliberately excluded it frm the instalation process. 

2013 was installed Click to RUn from Office 365, and Outlook was installed as well because we moved to Exchange online as part of our office 365 migration.

The only version of outlook that has ever been on this machine is the install of 2013.

Well, since Outlook was never in play, you obviously aren't using OOM (Outlook Object Model) in your Access code to invoke the emails which may or may not be at the heart of the problem. Guess is that you are using some variation of the DoCmd.SendObject method versus explicitly sending it via Outlook from within your code - question(s) that are probably best asked in the MS Access forum.

I am indeed using s DoCmd.sendobject.

I even have a few quickie reports that uses Macro command EmailDatabaseObject, and it does the same thing. 

This is so obviously an Outlook issue, as Outlook is failing to properly respond to it's own settings.  "Never warn" means NEVER warn, and yet it is ALWAYS warning.

I do have this question in the Access forums as well, and am getting just as far.

I would expect stock Microsoft products using stock commands designed to work together, to actually work together.

I would expect a mature email client to properly respond to it's own configurable settings.

Is this really asking too much?

I would expect a mature email client to properly respond to it's own configurable settings.

The configurable settings work just fine when attempting to send email via Outlook using OOM as opposed to the generic "default" email client approach (which would have been the case with GroupWise). Decided to humor myself and spent a few minutes to get reacquainted with Access using Outlook '2013 (have no idea whether this is the same with OL'2010 but suspect it is) and tested both approaches

(1) DoCmd.SendObject does invoke Outlook's security model but
(2) using the Outlook Object Model in code to send email via Outlook does not - works just fine and no security prompt is encountered

FWIW - using "Docmd.SendObject" is <not> the recommended approach when sending email via Outlook. Your choice as to whether you modify your code accordingly or live with the message.

Some sample code can be found here

DoCmd.SendObject Method (Access)
https://msdn.microsoft.com/en-us/library/ff197046.aspx?f=255&MSPPError=-2147217396

*** the above example is incomplete - you'll need to add Outlook to your references and handle the scenario accordingly in terms of whether or not Outlook is running when your Access code is run to use either GetObject(, "Outlook.Application") - if Outlook is running or CreateObject("Outlook.Application") if it's not.

Also, as a side comment, equally puzzled why you would continue to run Access '2010 for this if it otherwise works in '2013 (unless there are some other factors involved where whatever has been developed doesn't run in '2013). However that has nothing to do with the issue at hand.

I thought I had replied to this, apaprently, I did not.


Not to argue, but as a point of discussion:  You say that Docmd.SendObject is not the reccomended way to send email via Outlook.  So just to be clear, Microsoft Access Macros should not be used to send objects to Microsoft Outlook, even though that is the only option within a Macro to do so?  I hope you can agree with me that this makes no sense, considering that both of these programs are part of an office suite, designed (so they claim) to work together?

As to why I am still using 2010, we just migrated to 2013, and and if I had just jumped into 2013 whole hog, I would never have known whether the problem I am running into was an Access problem or an Outlook problem.  One change at a time is the safest way to do things.

To my issue, you say not to use docmd.sendbject, then send me a link to docmd.sendobject.  What am I missing here?

BTW, Thank you for your time.

Phil

Not to argue, but as a point of discussion:  You say that Docmd.SendObject is not the reccomended way to send email via Outlook. 

...............

To my issue, you say not to use docmd.sendbject, then send me a link to docmd.sendobject.  What am I missing here?

Honestly - not going to try and defend or argue against the merits of DoCmd.SendObject - been far too long since I've used MS Access for anything significant. That discussion belongs in the MS Access forum. I merely pointed out what worked and what didn't. Personally, once I find the path that works - don't spend any time (or very, very little) on something that doesn't - a philosophy I follow for just about everything especially when it comes to "all things development" - life is just too short. Whether the issue you've identified is a bug or by design is for others to determine involved with MS Access. Going to assume that the generic SendObject approach is for use when the default email client is not Outlook which would appear to be the case when you were using GroupWise.

As for the reason for sending the DoCmd.Sendobject link - purpose was very simple, that article showed the code samples of how to implement the use of Outlook for sending emails from within MS Access if you reviewed it.. Obviously the "SendObject" approach is triggering the Outlook Security Model which is what is generating your message.

Finally - all I did to do the test was create a simple module invoked by a macro to sidestep the Outlook Security Model which only took a few minutes remembering that I haven't used MS Access at that level in years. The solution (or work-around - whichever way you wish to describe it) is extremely simple to implement.

Ah. sorry.  I did not keep reading further down to see the alternative methods.  My bad.  Unfortunately, alternative  examples are just to send Email, and do not seem to include sending a query or other object along with it.

Without the ability to add the results of a query as an attachment, I am still dead in the water.

Without the ability to add the results of a query as an attachment, I am still dead in the water.

Adding attachments is simply a matter of becoming familiar with the Outlook Object Model - specifically the "Attachments" property of a mail item which is extremely simple to implement.

Attachments.Add Method (Outlook)
https://msdn.microsoft.com/en-us/library/office/ff869553.aspx?f=255&MSPPError=-2147217396

In this scenario, you're working from within Access using the <Access Object Model> so things like tables, queries, and view objects may be directly accessible to add as attachments (simply don't remember at this point) using the Access <AllQueries> object (https://msdn.microsoft.com/EN-US/library/office/ff822845.aspx). Can absolutely be done by exporting any object (table, query etc) first and then attaching the exported file. The current specifics is something you'll need to ask in the MS Access forum - just a matter of learning what the best approach is. Programming related questions/issues are outside the scope of this forum.